chore: cd workflow#3935
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3935 +/- ##
=======================================
Coverage 93.23% 93.23%
=======================================
Files 87 87
Lines 11696 11696
=======================================
Hits 10905 10905
Misses 791 791 🚀 New features to boost your workflow:
|
|
If I understand this right here, we can get rid of this "make a unique version script" since the version should be unqiuely identified by a commit and it doesn't really make sense to run this twice on the same commit |
…into chore/publish-metadata-package
|
@ilan-gold good point, that script is now gone |
|
I become so used to our own dev setup, I forget what doesn't happen by default! |
Yes, vcs versioning for zarr metadata would be great! I think we can define a regex that matches git tags like |
|
Ok will have a look in the morning! |
this adds a cd workflow for
zarr-metadatawe either publish to pypi, in which case the version declared in the package is used, or we publish to testpypi, in which case a synthetic, unique version is created to ensure that we never have a conflict on testpypi.
this workflow only supports workflow dispatch right now. later PRs will add a tag-based release workflow.
TODO:
docs/user-guide/*.mdchanges/